home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 22
/
Cream of the Crop 22.iso
/
comm
/
tie30.zip
/
README.TXT
< prev
next >
Wrap
Text File
|
1996-09-11
|
16KB
|
317 lines
Installation and Startup Guide for
Teamwork Information Exchange 3
This guide contains a instructions for installing and running Teamwork
Information Exchange.
System Requirements & Configuration
TIE may be run on any IBM compatible PC using DOS 3.3 or above
and is compatible with all network software that adheres to the
file sharing protocols of DOS 3.3 and above. TIE requires a
minimum of 400K of available conventional memory.
Configuration Requirement: A minimum of 31 file handles must be
available to run TIE. The following line should appear in the
CONFIG.SYS file of all workstations running TIE.
FILES=31
Values above 31 may be substituted if other applications require
more file handles. Values above 31 may be required if your
workstation is running memory resident (TSR) applications or
utilities such as shell programs.
Installing TIE On Your Network
For multi-user access, TIE's data files must be installed on a
network server or workstation where the data files can be shared.
To install TIE on the network server place the distribution disk
in drive A: and type the following command:
A:INSTALL
You will be prompted as follows:
Disk drive where you want to install: c Enter the drive
letter for the
network server drive
where you want to
install the program
and data files.
Suggested installation directory on drive X is \TIE3 where "X"
is the drive letter
specified above.
Press <Enter> key to accept or type a new path: press enter to
accept the default
directory or enter a
new directory name.
TIE's program and data files will be decompressed and installed
on the designated drive and directory.
The main program (TIE.EXE) may also be installed on and run from
individual workstations. Note that not all networks support
running workstation resident copies of TIE with access to the
data files on the server. We recommend that, were possible, the
program be installed on each work station. This configuration
reduces network traffic and improves performance. To install the
TIE main program on a network workstation, create a directory on
the workstation's hard disk and simply copy the main program file
(TIE.EXE) from the network server to the new subdirectory on the
workstation's hard disk. Example:
C: Change to the workstations hard drive
MD \TIE3 Create a subdirectory named TIE3
CD \TIE3 Select the new subdirectory
COPY G:\TIE3\TIE.EXE Copy TIE.EXE from the network server
drive to the workstation drive. Where
"G:" is the network server drive letter
where TIE was installed.
Starting TIE
TIE can be run from any DOS workstation on the network provided
that the workstation views the server drive as a standard DOS
disk drive. In many installations, access to the network
server's disk drive requires a local logon procedure before the
server volume is visible to the workstation. The following
assumes that you have already gained access to the network server
via your local log on procedure. Your network manager may have
provided you with a batch file that eliminates the need for
typing the individual commands.
TIE uses DOS environment settings to determine the location of
the server resident shared data files and the default directory
where files attached to mail messages will be saved. DOS
environment variables are normally setup in the workstation's
autoexec.bat file. The required environment variables are
specified as follows:
SET TIEDAT=g:\tie3 Where "g" is the network drive letter
where TIE's program and data files have
been installed. If not specified, the
default is the current drive and
directory.
SET TIEINBOX=c:\inbox Where "c:\inbox" is the workstation
drive and directory where the user will
normally save email attachments. If the
common use of file attachments in your
organization is for sending word
processing documents, you may wish to
set this to your word processor's
default document directory. If not
specified, the default is "c:\"
To run the server copy of the program, when TIE.EXE is not
resident on the workstation's hard disk, type the following
commands:
g: Where "g" is the network drive letter where
TIE's program and data files have been
installed.
CD \TIE3 Set the default directory to the directory
where TIE's program and data files have been
installed.
TIE Run TIE.
To run a workstation installed copy of the program with access to
the shared data files located on the network server, type the
following commands:
d:\tie3\tie Where "d" is the workstation drive letter where
TIE.EXE has been installed. TIE will look for
shared data files on the drive and directory
specified by the "TIEDAT" environment variable.
Your system manager will assign each authorized user, a unique
User ID which must be entered each time you start TIE.
Command line parameters are available for adjusting mouse
operation and improving network performance. See Appendix A for
details on command line parameters.
Establishing a System Operator
TIE is distributed with all data files empty. Because there are
no defined users in the system when TIE is first run, the log on
screen is temporarily bypassed and replaced by a data entry
screen which allows definition of an initial user. By default,
this initial user must be given the maximum (System Operator)
privileges in order that additional users can be added to the
system. When TIE initially starts for the first time, enter the
information requested for all fields. Be certain that you
memorize or write down your User ID before saving the entries.
Immediately after saving data on the user definition screen, the
logon screen will be displayed. After entering your User ID, you
will have full access to all program functions.
Appendix A - Command Line Parameters
When starting TIE from a command prompt, the command line
allows for specification of the location of shared data
files, optional mouse configuration parameters and optional
environment parameters. The order of parameters in the
command line is as follows:
TIE [mouse parameters] [environment parameters]
The brackets are not typed and are shown to indicate that
each parameter set is optional. Whenever the data drive and
directory is specified, it must be the first parameter on
the command line.
Mouse Parameters
In most instances it should not be necessary to enter any
mouse parameters on the command line. On EGA or better
monitors the mouse is displayed as a true mouse (arrow)
cursor. On other displays the mouse cursor is displayed as
a block cursor.
The mouse parameters that can be entered on the command line
are as follows:
/nv Disable video bit manipulations. You may want to
try this parameter just to see if you like the
screen appearance better.
/ng Disable graphic mouse cursor. If the mouse cursor
does not behave properly when running in a DOS
window under Windows 3.x you may need to use this
parameter.
If both parameters are used on the command line, a space is
required between them. Example: TIE /nv /ng
Special Note: If your monitor goes blank when starting TIE
or becomes distorted, using both the /nv and /ng parameters
should correct the problem. In addition, these parameters
are required when running the DOS version of TIE in less
than full screen mode under Windows.
Environment Parameters
Several environment parameters can be passed to TIE either
on the command line or through the SET CLIPPER environment
variable. The environment settings are as follows:
E:<nExpandedKB> The E option enables use of LIM 4.0 -
compatible EMS memory and can improve performance on
workstations that have EMS memory. If your system
is running EMM386, or another memory manager, you
can simulate EMS memory with the following command
in your config.sys file.
Device=C:\DOS\EMM386.EXE AUTO RAM
To use up to 512k of expanded memory, add "//e:512"
to the command line.
BADCACHE Some caches that use expanded (LIM) memory do
not expect that other applications will be using
expanded memory and can burst into memory segments
that TIE is using. The BADCACHE option provides a
way around this.
SWAPPATH <d:\directory> The virtual memory management
system used by TIE loads as much of the program into
memory as will fit. When additional code segments
are needed, the system swaps unneeded segments to
expanded memory and loads the required code. If
expanded memory is unavailable or exhausted, the
code segments are swapped to the default disk. The
SWAPPATH option allows these swap files to be
redirected to an alternative drive and directory.
To reduce network traffic and improve program
performance, the location where swap files are
written should be the local workstation's hard disk.
If TIE is installed on the workstation, this is the
default. Otherwise the SWAPPATH option should be
used.
TEMPPATH <d:\directory> Sorting and indexing routines in
TIE use temporary scratch files to buffer data as
they proceed. If the drive where the TIE resides
does not have enough disk space or is read only, an
alternate drive and directory can be specified.
Any one or more of these parameters may be passed to TIE on
the command line by entering two slashes before the first
parameter and separating each parameter with a semicolon.
Example:
TIE //E:512;SWAPPATH C:\TIE;TEMPPATH C:\TIE
Alternatively, these parameters may be declared at system
startup and passed to TIE from the "CLIPPER" environment
variable. Example:
SET CLIPPER=E:512;SWAPPATH C:\TIE;TEMPPATH C:\TIE
When placed in your autoexec.bat file, this line has the
same effect as passing the E, SWAPPPATH, and TEMPPATH
options on TIE's command line.
Troubleshooting
Out of Memory
If you receive an Out of Memory message when running this
program it means that you either do not have enough
conventional memory available to run the program or there is
a fault in expanded memory.
The amount of memory available for running applications can
also be increased removing unnecessary TSR programs (screen
savers, DOS shells, pop-ups, mouse drivers, etc.) If you
are using DOS version 5.0 or higher, you may be able to load
some of these programs into high memory.
Runtime Errors
The most serious type of potential problem is a run-time
error. If this occurs, it will cause the program to abort.
When this happens, the program will list several lines of
text which indicate the cause of the error and it's location
in the program's source code.
If you get a run-time error, make a note of the error
message. Run-time errors can be the result of errors in
data entry, improper system configuration, or failure to
have your printer on-line and ready when print operations
are being performed. Check your data using the browse
functions to be sure that you have entered it correctly.
Run the Reindex option from the file menu to insure that all
files are properly indexed. Also, check that your system is
properly configured ("FILES=31" in your CONFIG.SYS file,
printer turned on and on-line when printing reports).
Sharing Violation
On some networks a sharing violation can occur when two or
more users attempt to execute a portion of TIE the same
time. To solve this problem, set the file attribute of
TIE.EXE to read only. This can be done using the DOS
attribute command as follows:
ATTRIB +R drive:\TIE\TIE.EXE
It should never be necessary to change the file attribute on
a workstation installed program.
Getting Help
If you are unable to resolve a problem on your own, send us
a letter with the exact text of the error message (if any)
and a compete description of the problem, your computer
system (computer, memory, graphics card, DOS version, etc.),
the option you were running when the error occurred, and any
supplemental data which you entered under the option.
Sample printouts are often key to uncovering the source of a
problem. We will investigate the problem and respond as
quickly as possible.
If it's a simple problem or you just have a question, you
may want to call us at (301) 306-0409. You may also contact
us by Email on Compuserve at: 72144,1223 or Internet at:
72144.1223@compuserve.com.
